Before submitting the PR, please make sure you do the following

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• Prefix your PR title with feat:, fix:, chore:, or docs:.
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.
• If this PR changes code within packages/svelte/src, add a changeset (npx changeset).

Tests and linting

• Run the tests with pnpm test and lint the project with pnpm lint

I was trying to understand how svelte works under the hood so I created a diagram for it using code-canvas.com. I think it will be pretty helpful for contributors to quickly onboard to the inner-works of svelte.

Here is the generated diagram for svelte grouped by the application's use-cases and their runtime data flows: Open interactive diagram ->

I built code canvas to simulate a senior engineer who have been working on svelte's codebase for pretty long and can explain to you any functionality of the repository visually through diagrams.

Here is what users are saying about codecanvas

"I used to spend 4 hours asking GPT how a use case in a codebase works and I keep going back and forth until I am able to draw a diagram to summarize my understanding,
CodeCanvas gives me that diagram in 40 seconds"

Some Notes:

• The diagram is already generated, completely free, no monthly subscription.
• The diagram file is stored in the repository itself, so the readme link will only work after merging. Until then, you can view the diagram from the link I shared above.
• Read the 1 pager guide to learn how to refine simulations to capture specific codebase logics you might want to cover.
• You can reach me out anytime on discord discord.gg/t3ezMyMPqr